What's the difference between the Legacy API and the Taguchi API?

Last Updated: 4/9/2026     Tags: legacy api, api, v5 api, Integrations
  • Switch Version
  • V5
  • V4

This document outlines the status of the Legacy API and the benefits of the current Taguchi API.

Legacy API Status

The Legacy API remains available for existing integrations. Organizations can continue to use the Legacy API alongside the Taguchi API, with data remaining consolidated across both. For new integrations, Taguchi recommends using the Taguchi API.

Benefits of the Taguchi API

The Taguchi API (formally the V5 API) includes:

1. Flexible Authentication

  • Static API Tokens: Supports the use of static API tokens for authentication.
  • JWT Authentication: Supports JSON Web Token (JWT) authentication with:
    • Pre-shared keys
    • Public keys

2. Faster Setup

  • Self-Serve Setup: Enables self-serve setup for both authenticated and unauthenticated endpoints, simplifying integration with internal systems.
  • OpenAPI Specifications: Provides OpenAPI specifications that allow for:
    • Auto-generation of sample requests
    • Wrapper code generation using Postman and other API clients

3. Improved Performance

  • Batching Support: Taguchi API endpoints support batching of up to 1000 actions in a single request, resulting in significantly improved performance for high-volume applications.

Choosing an API

  • The Legacy API remains available for existing integrations.
  • The Taguchi API is recommended for all new integrations, to take advantage of its authentication options, self-serve setup and performance benefits.
  • For implementation details, refer to the V5 API documentation.

Support and Guidance

For assistance with your integrations, please contact our Client Success team or the Taguchi support team.